home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c.moderated,comp.lang.c
- Subject: Re: fflush(stdin) - not guaranteed to work?
- Date: 17 Apr 1996 10:45:35 -0500
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Sender: clc@solutions.solon.com
- Approved: clc@solutions.solon.com
- Message-ID: <4l33mv$7qf@solutions.solon.com>
- References: <4ksjpn$rjt@solutions.solon.com> <4ku3id$53h@solutions.solon.com> <4l1idn$pvs@solutions.solon.com>
- NNTP-Posting-Host: solutions.solon.com
-
- In article <4l1idn$pvs@solutions.solon.com>,
- News User Id <news@eskimo.com> wrote:
- >Before anyone goes off and looks and is disappointed (actually,
- >it's probably too late for that), the only system-specific
- >question that the comp.lang.c FAQ list answers in that much
- >detail is, "How do I read one character without waiting for
- >the RETURN key?". To the implicit followon question, "If
- >fflush(stdin) won't work, how *can* I flush the user's typeahead
- >before issuing a prompt confirming whether I should reformat the
- >hard drive?", the FAQ list suggests no answer, because I don't
- >know a good one (other than, your program probably shouldn't be
- >offering to do that at all).
-
- Ah, right. My apologies. I was thinking along the lines that these two problems
- are so closely related that the answer to one is really tied to the other.
- Though it doesn't have a ``canned'' answer for various platforms, the FAQ does
- give some leads in the right direction.
- --
- I'm not really a jerk, but I play one on Usenet.
-